Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Snapshots with missing or failed shards hang on restore operation #4701

Closed
imotov opened this issue Jan 13, 2014 · 0 comments · Fixed by #4702
Closed

Snapshots with missing or failed shards hang on restore operation #4701

imotov opened this issue Jan 13, 2014 · 0 comments · Fixed by #4702
Assignees
@imotov
Labels
>bug v1.0.0.RC1

Comments

@imotov
Copy link
Contributor

imotov commented Jan 13, 2014

To reproduce snapshot an index with unavailable primary shards and then try to restore it - the restore operation will hang. Expected result: restore operation should fail with an error.
@ghost ghost assigned imotov Jan 13, 2014
@imotov imotov mentioned this issue Jan 13, 2014
Merged
@imotov imotov closed this as completed in b987615 Jan 13, 2014
brusic pushed a commit to brusic/elasticsearch that referenced this issue Jan 19, 2014
@imotov @brusic
Improve support for partial snapshots
15a0190 
Fixes elastic#4701. Changes behavior of the snapshot operation. The operation now fails if not all primary shards are available at the beginning of the snapshot operation. The restore operation no longer tries to restore indices with shards that failed or were missing during snapshot operation.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@imotov imotov

Labels
>bug v1.0.0.RC1
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Improve support for partial snapshots imotov/elasticsearch
1 participant
@imotov